Monitoring Azure Web Jobs
Learn how to monitor Azure Web Jobs
Nodinite has monitoring for the following Azure Web Job types:
- Web Job - Triggered
- Web Job - Continuous
This page provides monitoring options for Azure Web Jobs using Nodinite from one or more role-based Monitor Views. Nodinite monitors Azure Web Jobs' operational outcome, as specified by user-defined thresholds, either global or specific. You can manage configured Azure Web Jobs; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Web Jobs page.
Example list of monitored Web Jobs in a Monitor View
Monitoring Features
- State Evaluation - Make sure the Web Jobs has the intended run-time state!
- Time-based - Make sure your Web Jobs run when expected.
- Duration check - Make sure your Web Jobs runs as fast as you expect.
- Last Run evaluation - monitors the outcome of runs.
If Nodinite can't check your Web Jobs state, chances are no one else can use or benefit from them either.
- Automatic Discovery
- Nodinite Azure agents use the Azure Rest API and offer you an automatic discovery of your Web Jobs. Sharing access to any individual Web Job is very easy from within Nodinite using Monitor Views.
- Category-based monitoring - To help you manage and monitor the different type of Web Jobs, the Resources groups by Categories:
State evaluation for Web Jobs
One (1) Web Job manifests within Nodinite as one Resource. If you have 42 deployed Web Jobs, then you will have 42 Resources in Nodinite.
- The name of the Resources is the same as the deployed Web Job in Azure.
- The following 'Web Job' Categories exists:
- Web Job - Triggered.
- Web Job - Continuous.
List of Web Jobs monitoring categories.
Many other Azure related Categories exists as well; please review the Azure Monitoring Overview
- The Application name uses physical deployment paths. This pattern guarantees uniqueness:
- subscription name/resource group name/App Service name
Example of Application naming pattern
- subscription name/resource group name/App Service name
Each Web Job (presented in Nodinite as a Resource) has one of the following evaluated states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Web Job' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached |
|
Edit thresholds | |
| Warning | Warning threshold is breached |
|
Edit thresholds | |
| OK | Within user-defined thresholds |
|
View History |
A common use case is a specific Web Job that you have configured. Then, someone accidentally removes it (for example your DevOps based automatic deployment fails to redeploy a business-critical Web Job)
Web Job example when not available
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
Last Run evaluation
The Nodinite Azure Web Jobs Logging and Monitoring agent evaluates the outcome of runs of Web Jobs. There will be one Resource for each Web Job available within Monitor Views where included.
Example of state evaluation where the last Run succeeded as seen in a Monitor View
Whenever a run fails, the Resource evaluates as being in the Error state. It remains in this state until a user clears the error.
Azure Subscriptions
Each configured Azure Subscription to monitor manifests as one Resource. Remote Actions exists to help you manage and get fast access to the Azure portal.
Example of the Azure Subscription configuration when a problem to log on is detected.
Manage the list of Azure Subscriptions from the Global Configuration.
Azure Resource Group
Each configured Azure Resource Group to monitor manifests as one Resource. Remote Actions exists to help you manage and get fast access to the Azure Resource Group using the Azure portal.
Manage the list of Azure Resource Groups from the Global Configuration.
Example of a 'log on' problem for the Azure Resource Group category.
Alert history for Web Jobs
During root cause analysis or other purposes, it might be useful to understand how often problems with your Web Jobs happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span for all your Web Jobs or individually. This topic is detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all Resources in the Monitor View |
 Alert history for the selected Web Job |
Frequently asked questions
You can find solutions to common problems and the FAQ in the troubleshooting guide.
How do I enable the monitoring of Web Jobs?
To Monitor Web Jobs, configure the Agent with the Enable monitoring checkbox (checked by default). The details are available in the 'Configuration' user guide.
The screenshot from the remote configuration form is from the Monitoring Agents administration page.
Example with monitoring for Web Jobs disabled.